Keybase client cli on Netbsd (using procfs on NetBSD) #19061
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are really relatively minor changes (just adding
netbsdbuild headers to files) that get me a working Keybase cli client on NetBSD. As such I see little harm in merging them in.I'm relying on NetBSD's linux emulation and the fact that that gives me a profs (
/proc). With this the cli seems to work perfectly - i.e. it launches the server to the background. I can read and send chats. It's great 😄This was inspired by dressupgeekout's post which I had initially followed. But then I wanted to build a more recent version and so ended up with these changes.
go-ps/process_netbsd.gofile from dressupgeekout's approach and instead use thego-ps/process_unix.gofor netbsd since I can take advantage of procfs on NetBSD.Ultimately I would like to get a proper
go-ps/process_netbsd.goapproach working on NetBSD, but at the moment although it builds fine I can't get the tests to pass so that's why I've just gone for the procfs approach with this PR.The only downsides I see with this PR is that some NetBSD users might be able to have this build and then not work because they don't have a procfs.